QRZ! Ham Radio 5/QRZ Ham Radio Callsign Database - Volume 5.iso/digests/tcp/940010.txt

Internet Message Format | 1994-11-13 | 12.7 KB

Date: Fri, 14 Jan 94 04:30:02 PST
From: Advanced Amateur Radio Networking Group <[e-mail]>
Errors-To: [e-mail]
Reply-To: [e-mail]
Precedence: Bulk
Subject: TCP-Group Digest V94 #10
To: tcp-group-digest


TCP-Group Digest            Fri, 14 Jan 94       Volume 94 : Issue   10

Today's Topics:
                          JNOS and BPQ Code
                        KISS and SLIP (3 msgs)
                       TCP-Group Digest V94 #8
                       TCP-Group Digest V94 #9
                                TNC3?
                   Wampes & Ethernet card (2 msgs)

Send Replies or notes for publication to: <[e-mail]>.
Subscription requests to <[e-mail]>.
Problems you can't solve otherwise to [e-mail].

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Fri, 14 Jan 94 08:56:00 PST
From: Martin Lines <[e-mail]>
Subject: JNOS and BPQ Code
To: "'nos-bbs'" <[e-mail]>, tcp-group <[e-mail]>

I originally wrote to the group to find out if anyone has similar problems
to myself at integrating
JNOS and BPQ switches. Using the jnos built in bpq support I was unable to
get an interconnect
between the two cohabiting switches.

I have since discovered that using the commands "ax25 maxframe", "ax25
retry" or "ax25 window" in
either the startup script or from the command line stop this interlink
working. Even a plain "ax25 maxframe"
query with specifying a port or value will kill this interlink.

I have removed all references to the above commands in the autoexec.nos and
I am happily switching
between JNOS and BPQ but this is not necessarily ideal.


Anyone have any further ideas/comments?

Martin - G1SEO

------------------------------

Date: Wed, 12 Jan 1994 22:15:26 -0800
From: [e-mail] (Phil Karn)
Subject: KISS and SLIP
To: [e-mail]

After thinking about it some more, I should moderate my statement a
bit.  Controllers that use special-purpose hardware to do things that
general purpose CPUs can't do (or do very well) are often
okay. Ethernet interfaces are a good example, as are DSP cards
(including modems).  HDLC interfaces are a third.

What I oppose are "smart" controllers that use *general purpose* CPUs.
These almost never make sense, except in very special situations where
the main host's interrupt latency is too long to service the hardware
fast enough. As Van Jacobsen likes to say, there are all too many
examples of a high speed Sparcstation CPU twiddling its thumbs waiting
for a Z-80 controller CPU to finish its job...

Sometimes, though, you don't have a choice. An example is running
packet on a laptop that doesn't have a PCMCIA slot for an HDLC
interface. In this case, you *must* use an interface that already
exists. The serial or parallel ports, for example, with a KISS
TNC. GPIB is not a good choice, not because of anything good or bad
about it technically, but simply because it is not widely supported in
mass market computers. If I have to add GPIB directly to the computer,
then I might as well plug in a HDLC board like the DRSI card.

Phil

------------------------------

Date: Thu, 13 Jan 94 13:06:00 -0000
From: [e-mail] (Mike Bilow)
Subject: KISS and SLIP
To: [e-mail]

Cc: [e-mail]


 JS> Another option might be to use IEEE488 (or HPIB, GPIB, IEC625, whatever
 JS> you prefer).
* * *
 JS> To test this idea I have built a simple add-on interface for a TNC2
 JS> which consists of 5 chips (a GAL, a latch, a NEC TLC7210 IEC-bus

As I recall, HP was asserting patent rights on the three-wire handshake used in
IEEE-488?  I think this has been one of the main obstacles to its wider
adoption.

It seems like a technically nice idea, although I think that limiting the bus
to 15 devices is the kind of fundamental design error we will be certain to
regret later, much like the SSID field in AX.25.

 JS>  Jan Schiefer, g0trr, [e-mail], HP Labs Bristol, UK.

I hope you are not the person assigned to collect the royalties!

-- Mike

------------------------------

Date: Wed, 12 Jan 1994 22:15:26 -0800
From: [e-mail] (Phil Karn)
Subject: KISS and SLIP
To: [e-mail]

After thinking about it some more, I should moderate my statement a
bit.  Controllers that use special-purpose hardware to do things that
general purpose CPUs can't do (or do very well) are often
okay. Ethernet interfaces are a good example, as are DSP cards
(including modems).  HDLC interfaces are a third.

What I oppose are "smart" controllers that use *general purpose* CPUs.
These almost never make sense, except in very special situations where
the main host's interrupt latency is too long to service the hardware
fast enough. As Van Jacobsen likes to say, there are all too many
examples of a high speed Sparcstation CPU twiddling its thumbs waiting
for a Z-80 controller CPU to finish its job...

Sometimes, though, you don't have a choice. An example is running
packet on a laptop that doesn't have a PCMCIA slot for an HDLC
interface. In this case, you *must* use an interface that already
exists. The serial or parallel ports, for example, with a KISS
TNC. GPIB is not a good choice, not because of anything good or bad
about it technically, but simply because it is not widely supported in
mass market computers. If I have to add GPIB directly to the computer,
then I might as well plug in a HDLC board like the DRSI card.

Phil

------------------------------

Date: Thu, 13 Jan 94 20:51:32 UTC
From: [e-mail]
Subject: TCP-Group Digest V94 #8
To: [e-mail]

Hello People...

This message is concerning the problem with changing drives durning an FTP
session...  This is what I have noticed.


Edited Trace of an FTP Session to Local Station
------------------------------------------------
Resolving n8wei... Trying 44.102.128.18:ftp...

Local Directory - E:/NOS/PUB/INCOMING

FTP session 2 connected to n8wei

220- N8WEI.AMPR.ORG, JNOS FTP version 1.10x15 (80386)
220-
220- N8WEI TCP/IP P.B.B.S.
220- 4245 Stonebridge Rd. SW  Apartment #9, Wyoming, Michigan, U.S.A.  49509
220-
220  Ready on Thu Jan 13 20:56:52 1994

331 Enter PASS command
230 Logged in

ftp> pwd
257 "/" is current directory

ftp> lcd
Local Directory - E:/NOS/PUB/INCOMING

ftp> cd d:\
553 Can't read directory "/d:": No such file or directory

ftp> lcd d:\
Local Directory - D:/

ftp> cd f:\borlandc\wg7j
553 Can't read directory "/f:/borlandc/wg7j": No such file or directory

ftp> lcd f:\borlandc\wg7j
Local Directory - F:/borlandc/wg7j

ftp> lcd code
Local Directory - F:/borlandc/wg7j/code

ftp> ldir

convers.zip      12,202 21:31  1/06/94   desc.ftp            3  6:32  1/07/94
dhe1_x15.zip     22,436 21:40  1/06/94   hkmmods.zip         0 23:27  1/11/94
hkmnos1.zip     287,232 18:19  1/12/94   iw5dhe1.zip    22,385 21:50  1/06/94
jn110x14.zip  1,077,992  1:01 12/11/93   kissv4-3.obj    2,061 21:51  1/06/94
knxmd15a.zip      8,336 21:57  1/06/94   knxmd15b.zip   32,010 22:39  1/11/94
knxmd15c.zip     31,189  8:31  1/12/94   knxmod15.zip  130,639  8:20  1/12/94
knxtrace.zip     41,941  8:45  1/12/94   newx15.zip    101,698  1:23 12/11/93
nos-span.zip          0 23:04  1/11/94
15 files. 1,286,144 bytes free. Disk size 43,196,416 bytes.


ftp> lcd e:\nos\pub\incoming
Local Directory - E:/nos/pub/incoming

ftp> ldir

archie.man       39,026 13:58  1/07/94   beavis.gif      4,849 22:35 10/17/93
delay.com         9,002 21:56  1/11/94   lan_gifs.zip   15,807 13:00 11/17/93
menumous.zip      2,647 14:09  1/07/94   n8wei.txt      13,484 19:20  1/13/94
n8wei-1.gif      29,241 18:04  9/05/93   n8wei-2.gif     8,931  0:58 11/21/93
n8wei-3.gif       9,113  1:01 11/21/93   nos.exe       212,236  7:59  1/12/94
nos-tree.zip        881 21:05  1/11/94   reset.com       3,140 21:11 12/13/93
rewrite           2,454 19:08  1/13/94   upbob.txt         292 15:51  1/07/94
uptodd.txt          300 15:48  1/07/94   wg7j-nos.ico      766 18:13 11/18/93
16 files. 4,259,840 bytes free. Disk size 11,427,840 bytes.


ftp> quit

221 Goodbye!

FTP session 2 closed: EOF
Hit enter to continue
------------------------------------------------

As you can clearly see, I can change drives with the LCD command, but not the
CD command.  In otherwords, when I FTP someone, I can change my Local
Directory, but I can not change the remote directory....

It seams to me that if this is allowed, and possible on the local station,
that it should be possible on the remote station...  BUT...  You will notice
that the CD command places a '/' in front of the directory name that you
enter.  I wonder, does it do this when it tries to switch directories, or just
when it displays the error...???  Hmmmm.....  If it does this before it tries
to perform the command, couldn't we just change it so that if there is a ':'
contained in the second character of the string, we just don't put the '/' in
front of the string...

I will attempt to look at this, and I will post my findings here...


73  DE  N8WEI...

C-Ya'...

    *---------------------------------*------------------------------------*
    |  ((N8WEI) TCP/IP) PBBS 147.560  |       Todd W. Powers (N8WEI)       |
    | ------------------------------- |      4245 Stonebridge Road SW      |
    | Packet Radio:                   |         Wyoming, MI  49509         |
    |   N8WEI @ N8WEI.AMPR.ORG        | ---------------------------------- |
    |   N8WEI @ N8WEI.#SWMI.MI.USA.NA |                                    |
    | Internet:                       |  Borland C++ & FoxPro Programmer   |
    |   N8WEI @ HAMGATE.GVSU.EDU      |                                    |
    *---------------------------------*------------------------------------*

------------------------------

Date: Thu, 13 Jan 1994 14:33:04 GMT+0200
From: "Jack Stiekema, PE0MOT" <[e-mail]>
Subject: TCP-Group Digest V94 #9
To: Advanced Amateur Radio Networking Group <[e-mail]>

->Another option might be to use IEEE488 (or HPIB, GPIB, IEC625, whatever
->
->To test this idea I have built a simple add-on interface for a TNC2
->
->I'd be happy to hear any comments about this approach. Ah yes, and the
->PC interface is just as trivial and cheap as the TNC one.
Looks ok, but how cheap is the pc interface?

Kind regards,
Jack
+----------------------------------------------------+
| Victron bv   POB 31   9700 AA Groningen   Holland  |
|   phone: [phone]   fax: [phone]        |
+----------------------------------------------------+

------------------------------

Date: Fri, 14 Jan 1994 01:15:44 -0800
From: [e-mail] (Phil Karn)
Subject: TNC3?
To: [e-mail]

I have had a TNC-3 for years. I haven't used it in a long time, but it
might still be around here somewhere.

The TNC-3 came out sometime in the middle 1980's, shortly after TAPR
released the TNC-2.  It's yellow, about 8-10cm long and perhaps 1 x 2
cm in its other dimensions. It appears to be constructed entirely of
polystyrene. To transmit, you put one end into your mouth and hum.

Most people would call it a kazoo. But it clearly says "TNC-3" on the
side, so that's what it must be.

I'm not kidding -- one of the smaller packet accessory manufacturers,
based on Long Island, I think, actually made up and gave away a whole
bunch of these things as promotional items.

So I guess that means the next TNC should be called the TNC-4.

Phil

------------------------------

Date: Thu, 13 Jan 94 18:16:58 MET
From: [e-mail]
Subject: Wampes & Ethernet card
To: [e-mail]


    I run the wampes program (931106) on a RISC 6000 machine. I hoped that
wampes program knows automaticaly the interface attached on this machine, but
it din't.

    So i want to know how "say" to wampes (attach) that i've got an ethernet
card.

    Thanks a lot.

    73 From Curro eb3aod
    e-mail: [e-mail]
    BBS-AX25: eb3aod @ ea3rdt.eat.esp.eu


------------------------------

Date: Thu, 13 Jan 94 17:30:48 MST
From: Dieter Deyke <[e-mail]>
Subject: Wampes & Ethernet card
To: [e-mail], [e-mail]

>       I run the wampes program (931106) on a RISC 6000 machine. I hoped that
> wampes program knows automaticaly the interface attached on this machine, but
> it din't.
>
>       So i want to know how "say" to wampes (attach) that i've got an ethernet
> card.

WAMPES will NOT talk  directly to the ethernet  interface  card, this is
the job of the UNIX networking kernel.

--
Dieter Deyke - [e-mail] - [e-mail]

------------------------------

End of TCP-Group Digest V94 #10
******************************